System, method, and computer-readable medium for abbreviated-code dialing in a network system

ABSTRACT

A system, method, and computer readable medium for abbreviated dialing in a femtocell network is provided. A user having authorized access to the femtocell network may dial another authorized user using an abbreviated code. On receipt of the call request, a femtocell system may evaluate the destination number to determine if it is an abbreviated code. If the dialed number is not an abbreviated code, the femtocell system may direct the call request to the telecommunication core network for processing thereby. If the dialed number is evaluated by the femtocell system as an abbreviated code, the femtocell system may direct the call request to an on-site PBX for call handling. If the abbreviated code is a valid code and the dialed user equipment is currently in the femtocell network service area, the PBX may then complete the call setup within the femtocell network.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/729,895 entitled SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR ABBREVIATED-CODE DIALING IN A NETWORK SYSTEM, filed on Dec. 28, 2012, now issued U.S. Pat. No. 9,055,581 issued on Jun. 9, 2015, which is a continuation of U.S. patent application Ser. No. 12/252,226 entitled SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUM FOR ABBREVIATED-CODE DIALING IN A NETWORK SYSTEM, filed on Oct. 15, 2008, now issued U.S. Pat. No. 8,346,216, issued on Jan. 1, 2013, which in turn claim priority to U.S. provisional patent application Ser. No. 61/003,151 entitled SIP-IOS ADAPTER FUNCTION filed Nov. 15, 2007, the disclosure of each of which are incorporated in their entirety herein by reference.

FIELD OF THE INVENTION

The present invention is generally related to radio access technologies and, more particularly, to mechanisms for abbreviated dialing in a network system.

BACKGROUND OF THE INVENTION

Contemporary cellular radio systems, or mobile telecommunication systems, provide an over-the-air interface to wireless user equipments (UEs) via a radio access network (RAN) that interfaces with at least one core network. The RAN may be implemented as, for example, a CDMA2000 RAN, a Universal Mobile Telecommunications System (UMTS) RAN, a Global System for Mobile communications (GSM) RAN, or another suitable radio access network implementation. A UE may comprise, for example, a mobile terminal such as a mobile telephone, a laptop computer featuring mobile telephony software and hardware, a personal digital assistant (PDA), or other suitable equipment adapted to transfer and receive voice or data communications with the radio access network.

A RAN covers a geographical area comprised of any number of cells each comprising a relatively small geographic area of radio coverage. Each cell is provisioned by a cell site that includes a radio tower, e.g., a base transceiver station (BTS), and associated equipment. BTSs communicate with UEs over an air interface within radio range of the BTSs.

Numerous BTSs in the RAN may be communicatively coupled to a base station controller, also commonly referred to as a radio network controller (RNC). The BSC manages and monitors various system activities of the BTSs serviced thereby. BSCs are coupled with at least one core network.

BTSs are typically deployed by a carrier network in areas having a high population density. The traffic capacity of a cell site is limited by the site's capacity and affects the spacing of cell sites. In suburban areas, sites are often up to two miles apart, while cell sites deployed in dense urban areas may be as close as one-quarter of a mile apart. Because the traffic capacity of a cell site is finitely limited, as is the available frequency spectrum, mobile operators have a vested interest in technologies that allow for increased subscriber capacity.

A microcell site comprises a cell in a mobile phone network that covers a limited geographic area, such as a shopping center, hotel, airport, or other infrastructure that may have a high density mobile phone usage. A microcell typically uses power control to limit the radius of the microcell coverage. Typically a microcell is less than a mile wide.

Although microcells are effective for adding network capacity in areas with high mobile telephone usage, microcells extensively rely on the RAN, e.g., a controlling BSC and other carrier functions. Because contemporary BSCs have limited processing and interface capacity, the number of BTSs—whether microcell BTSs or typical carrier BTSs—able to be supported by the BSC or other RAN functions is disadvantageously limited.

Contemporary interest exists in providing enterprise and office access, including small office/home office (SOHO) radio access, by an even smaller scale BTS. The radio coverage area of such a system is typically referred to as a femtocell. In a system featuring a femtocell, a UE may be authorized to operate in the femtocell when proximate the femtocell system, e.g., while the UE is located in the SOHO. When the UE moves beyond the coverage area of the femtocell, the UE may then be serviced by the carrier network. The advantages of deployment of femtocells are numerous. For instance, mobile users frequently spend large amounts of time located at, for example, home, and many such users rely extensively on cellular network service for telecommunication services during these times. For example, a recent survey indicated that nearly thirteen percent of U.S. cell phone customers do not have a landline telephone and rely solely on cell phones for receiving telephone service. From a carrier perspective, it would be advantageous to have telephone services provisioned over a femtocell system, e.g., deployed in the user's home, to thereby reduce the load, and effectively increase the capacity, on the carrier RAN infrastructure. However, various issues related to provisioning of exchange services in a femtocell network remain unresolved.

Therefore, what is needed is a mechanism that overcomes the described problems and limitations.

SUMMARY OF THE INVENTION

The present invention provides a system, method, and computer readable medium for call processing in a network system. A communication system features an IP-based femtocell system for provisioning communication services to a user equipment. Abbreviated dialing is supported by the femtocell network operating in conjunction with an on-site PBX or a SIP switch. A user having authorized access to the femtocell network may dial another authorized user using an abbreviated code, e.g., a 4-digit code comprising the 4-digit station number. On receipt of the call request, the femtocell system may evaluate the destination number to determine if it is an abbreviated code. If the dialed number is not an abbreviated code, the femtocell system may direct the call request to the telecommunication core network for processing thereby. If the dialed number is evaluated by the femtocell system as an abbreviated code, the femtocell system may direct the call request to the PBX or SIP switch for call handling. In this instance, the PBX or SIP switch may determine if the abbreviated code is a valid code, i.e., if it is assigned to an authorized UE. If so, the PBX or SIP switch may then determine if the dialed UE is currently in the femtocell network service area. In the event the dialed UE is in the femtocell network service area, the PBX or SIP switch may then complete the call setup within the femtocell network. If the PBX or SIP switch determines that the dialed UE is not currently in the femtocell network service area, the PBX or SIP switch may direct the call request to the telecommunication core network for processing of the call setup.

In one embodiment of the disclosure, a method of call processing in a network system is provided. The method includes receiving, by a femtocell system, a call setup request from a first user equipment, performing an evaluation of a destination number of a second user equipment to which the call is directed, and determining, based on results of the evaluation, the call setup request is to be directed to one of a private branch exchange deployed in a femtocell network and a telecommunication core network communicatively coupled with the femtocell network.

In a further embodiment of the disclosure, a computer-readable medium having computer-executable instructions for execution by a processing system, the computer-executable instructions for call processing in a network system is provided. The computer-readable medium comprises instructions that receive, by a femtocell system, a call setup request from a first user equipment, perform an evaluation of a destination number of a second user equipment to which the call is directed, wherein the evaluation determines if the destination number comprises an abbreviated code, and determine, based on results of the evaluation, the call setup request is to be directed to one of a private branch exchange deployed in a femtocell network and a telecommunication core network communicatively coupled with the femtocell network.

In a further embodiment of the disclosure, a system configured for call processing in a network system is provided. The system includes a packet-switched network, an IP Multimedia subsystem communicatively coupled with the packet-switched network, and a femtocell network communicatively coupled with the packet-switched network that includes a private branch exchange that maintains a data structure that associates directory numbers of authorized user equipments with abbreviated codes. The femtocell network includes a femtocell system that receives a call setup request from a first user equipment, performs an evaluation to determine whether a destination number of a second user equipment to which the call setup request is directed comprises an abbreviated code, and determines, based on results of the evaluation, the call setup request is to be directed to one of the private branch exchange and the IP Multimedia subsystem.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the following detailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network system that includes a cellular network adapted to provide macro-cellular coverage;

FIG. 2 is a diagrammatic representation of a conventional network system configuration featuring a femtocell;

FIG. 3 is a diagrammatic representation of a network system in which a femtocell system implemented in accordance with an embodiment of the present invention may be deployed;

FIG. 4A is a simplified diagrammatic representation of the femtocell system depicted in FIG. 3 that may be connected with an IP backhaul in accordance with an embodiment;

FIG. 4B is a simplified diagrammatic representation of an alternative embodiment of a femtocell system that may be connected with an IP backhaul;

FIG. 5 is a diagrammatic representation of an exemplary session initiation protocol registration message generated by a femtocell system on behalf of a user equipment in accordance with an embodiment;

FIG. 6 is a diagrammatic representation of a network system featuring a femtocell network implemented in accordance with an embodiment;

FIG. 7 is a diagrammatic representation of an exemplary software configuration of a user equipment adapted for engaging in communications with femtocell systems in accordance with an embodiment;

FIG. 8 is a diagrammatic representation of a PBX data structure that facilitates abbreviated code dialing within a femtocell network in accordance with an embodiment;

FIG. 9 is a flowchart that depicts a femtocell call processing routine implemented in accordance with an embodiment; and

FIG. 10 is a flowchart that depicts a PBX call processing routine implemented in accordance with an embodiment

DETAILED DESCRIPTION OF THE INVENTION

It is to be understood that the following disclosure provides many different embodiments or examples for implementing different features of various embodiments. Specific examples of components and arrangements are described below to simplify the present disclosure. These are, of course, merely examples and are not intended to be limiting.

FIG. 1 is a diagrammatic representation of a network system 100 that includes a cellular network 110 adapted to provide macro-cellular coverage to a user equipment. Cellular network 110 may comprise, for example, a code-division multiple access (CDMA) network, such as a CDMA-2000 network.

Cellular network 110 may include any number of base transceiver stations (BTSs) 112 a-112 c communicatively coupled with a base station controller (BSC) 114 or RNC. Each individual BTS 112 a-112 c under the control of a given BSC may define a radio cell operating on a set of radio channels thereby providing service to a user equipment (UE) 125, such as a mobile terminal. BSC 114 manages the allocation of radio channels, receives measurements from mobile terminals, controls handovers, as well as various other functions as is understood. BSC 114 is interconnected with a mobile services switching center (MSC) 116 that provides mobile terminal exchange services. BSC 114 may be additionally coupled with a packet data serving node (PDSN) 118 or other gateway service that provides a connection point between the CDMA radio access network and a packet network, such as Internet 160, and provides mobility management functions and packet routing services. MSC 116 may communicatively interface with a circuit switched network, such as the public switched telephone network (PSTN) 150, and may additionally be communicatively coupled with an interworking function (IWF) 122 that provides an interface between cellular network 110 and PSTN 150.

System 100 may also include a signaling system, such as a signaling system #7 (SS7) network 170. SS7 network 170 provides a set of telephony signaling protocols which are used to set up the vast majority of the world's PSTN telephone calls. SS7 network 170 is also used in cellular networks for circuit switched voice and packet-switched data applications. As is understood, SS7 network 170 includes various signaling nodes, such as any number of service control points (SCPs) 172, signal transfer points (STPs) 174, and service switching points (SSPs) 176.

BTSs 112 a-112 c deployed in cellular network 110 may service numerous network 110 subscribers. Cell cites provided by BTSs 112 a-112 c commonly feature site ranges of a quarter to a half mile, e.g., in densely populated urban areas, to one to two miles in suburban areas. In other remotely populated regions with suitable geography, site ranges may span tens of miles and may be effectively limited in size by the limited transmission distance of relatively low-powered UEs. As referred to herein, a cell provided by a BTS deployed in carrier network 110 for access by any authorized network 110 subscriber is referred to as a macrocell.

FIG. 2 is a diagrammatic representation of a conventional network system 200 configuration featuring a femtocell. In the depicted example, a central BSC 214 deployed in a cellular carrier network 210 may connect with a soft switch core 212 that is connected with a MSC 216. MSC 216 connects with the cellular core network and may interface with other networks, such as the PSTN as is understood. BSC 214 may be connected with and service numerous BTSs 212 a-212 c that provide macrocells to cellular network 210 subscribers.

BSC 214 may additionally connect with a tunnel gateway system 218 that is adapted to establish secured tunnels 232 a-232 x with respective femtocell systems 250 a-250 x. Femtocells comprise cellular access points that connect to a mobile operator's network using, for example, a residential DSL or cable broadband connection. Femtocells 250 a-250 x provide a radio access point for UE 225 when the UE is within range of a femtocell system with which the UE has authorized access. For example, femtocell system 250 a may be deployed in a residence of the user of UE 225. Accordingly, when the user is within the residence, mobile telecommunications may be provided to UE 225 via an air-interface provided by femtocell system 250 a. In this instance, UE 225 is effectively offloaded from the macro BTS, e.g., BTS 212 a, and communications to and from the UE are carried out with femtocell system 250 a over Internet 260. Thus, femtocell systems 250 a-250 x may reduce the radio resource demands by offloading UEs from macrocells to femtocells and thereby provide for increased subscriber capacity of cellular network 210.

In contemporary implementations such as that depicted in FIG. 2, a femtocell system 250 a comprises a transceiver without intelligence and is thus required to be connected and managed by BSC 214. Thus, femtocell systems 250 a-250 x are reliant on the carrier network centralized BSC 214 which has limited capacity and thus does not exhibit desirable scaling characteristics or capabilities. Moreover, high communications overhead are realized by the BTS backhaul.

FIG. 3 is a diagrammatic representation of a network system 300 in which a femtocell system implemented in accordance with an embodiment of the invention may be deployed. System 300 includes a radio access network (RAN) 310 that provides an over-the-air interface with a UE 325, e.g., a mobile terminal. RAN 310 may comprise, for example, a CDMA radio access network or another suitable RAN. RAN 310 may comprise various BTSs and associated base station controllers BSCs as well as other infrastructure as is understood. UE 325 may be implemented as a personal digital assistant (PDA), a mobile phone, a computer, or another device adapted to interface with RAN 310.

System 300 may include an IP Multimedia Subsystem (IMS) 320 architecture adapted to provide IP service to UE 325. To this end, RAN 310 is communicatively coupled with a serving general packet radio service (GPRS) support node (SGSN) 314 and a gateway GPRS support node (GGSN) 316. SGSN 314 provides the delivery of data packets from and to UE 325 within its service area. GGSN 316 provides an interface between the GPRS backbone network and external packet data networks. GGSN 316 is communicatively coupled with a policy decision function (PDF) 318 that provides authorization of media plane resources, e.g., quality of service (QoS) authorizations, policy control, bandwidth management, and the like. PDF 318 may be communicatively coupled with a call session control function (CSCF) 320.

CSCF 320 comprises various session initiation protocol (SIP) servers or proxies that process SIP signaling packets in IMS 320. CSCF 320 may include a proxy-CSCF (P-CSCF) that provides a first point of contact for an IMS-compliant UE. The P-CSCF may be located in the visited network, or in the UE's home network if the visited network is not fully IMS-compliant. UE 325 may discover the P-CSCF, e.g., by using Dynamic Host Configuration Protocol (DHCP), or by assignment in a packet data protocol (PDP) context. CSCF 320 additionally includes a Serving-CSCF (S-CSCF) that comprises the central node of the signaling plane. The S-CSCF comprises a SIP server, but additionally performs session control. The S-CSCF is located in the home network and interfaces with a home subscriber server (HSS) 340 to download and upload user profiles. CSCF 320 further includes an Interrogating-CSCF (I-CSCF) that comprises a SIP function located at the edge of an administrative domain. The I-CSCF has an IP address that is published in the Domain Name System (DNS) 372 that facilitates location of the I-CSCF by remote servers. Thus, the I-CSCF is used as a forwarding point for receipt of SIP packets within the domain. CSCF 320 may interface with an IP switch, such as a SIP switch 380. SIP switch 380 includes a Registrar 382 that processes register requests and provides location and contact information to a location server 384.

HSS 340 comprises a user database that supports the IMS network entities that manage calls. HSS 340 stores user profiles that specify subscription-related information of authorized users, authenticates and authorizes users, and provides information about the user's physical location. Various application servers (AS) 342 a-342 n that host and execute services interface with CSCF 320 via SIP.

CSCF 320 is coupled with a breakout gateway control function (BGCF) 322 that comprises a SIP server that provides routing functionality based on telephone numbers. BGCF 322 is used when a UE places a call from the IMS to a phone in a circuit switched network, e.g., PSTN 330, or the public land mobile network. A media gateway controller Function (MGCF) 324 performs call control protocol conversion between SIP and ISDN User Part (ISUP) and interfaces with a signaling gateway (SGW) 326. SGW 326 interfaces with the signaling plane of a circuit switched network, e.g., PSTN 330. SGW 326 may transform lower layer protocols, such as Stream Control Transmission Protocol (SCTP), into the Message Transfer Part (MTP) protocol, and pass ISUP data from MGCF 324 to PSTN 330 or another circuit switched network. A media gateway (MGW) 328 interfaces with the media plane of PSTN 330 or another circuit switched network by converting data between real-time transport protocol (RTP) and pulse code modulation (PCM), and may also be employed for transcoding when the codecs of the IMS and circuit switched networks differ. Resources of MGW 328 are controlled by MGCF 324. Fixed access, e.g., IP telephony devices 374 a-374 b, may connect with IMS network via Internet 370 that is communicatively coupled with IMS network 320 by way of border gateway 360.

As is understood, DNS 372 comprises a scalable namespace that facilitates access to entities deployed on the Internet or private networks. DNS 372 maintains various records for host names, servers, and the like. For example, DNS 372 maintains records (commonly referred to as “A records”) that map hostnames to IP addresses, pointer (PTR) records that map IP addresses to canonical names to facilitate reverse DNS lookups, service (SRV) records that specify information on available services, naming authority pointer (NAPTR) records that facilitate regular expression based rewriting, and various other records. DNS 372 may additionally include a telephone number mapping (ENUM) system that facilitates resolution of SIP addresses from E.164 number as is understood.

A base station manager (BSM) 378 may be deployed in Internet 370 and may be adapted to communicate with numerous femtocell systems and femtocell networks. BSM 378 may provide various operations, maintenance, and management functions to femtocell systems. For example, BSM 378 may provide service provisioning of femtocell systems, e.g., by providing configuration downloads to femtocell systems and preloading default configuration data for femtocell systems distributed via sales channels. BSM 378 may provide various support and maintenance features, such as alarm and periodic statistics reporting, automatic remote software image distribution to femtocell systems, provide upgrades and reconfigurations, and may provide remote access via Internet 370 for diagnostics and customer support.

In accordance with an embodiment, a femtocell system 350 may include integrated BTS and BSC functions and may feature additional capabilities available in the provided femtocell site coverage area. Femtocell system 350 provides an IP-accessible radio access network, is adapted for operation with IMS 320, and provides radio link control functions. Femtocell system 350 may be communicatively coupled with Internet 370 via any variety of backhaul technologies, such as an 802.11x link, a 10/100 BaseT LAN link, a T1/E1 Span or fiber, cable set top box, DSL modem connected with a central office digital subscriber line access multiplexer, a very small aperture terminal (VSAT), or another suitable backhaul infrastructure.

Femtocell system 350 may include a session initiation protocol (SIP) adapter that supports a SIP client pool and provides conversion of call set-up functions to SIP client set-up functions. For example, a SIP client pool allocated by femtocell system 350 may comprise a plurality of SIP user agents 352 a-352 c that each may be allocated for a UE authorized to access femtocell system 350. Additionally, femtocell system 350 includes electronic serial number (ESN) screening, and/or Mobile Equipment Identifier (MEID) screening, to allow only designated UEs to access the femtocell thereby restricting access to authorized home or small office UEs. For example, femtocell system 350 may be configured with an ESN and/or MEID list 354 that specifies ESNs and/or MEIDs of UEs authorized to access femtocell system 350. In the illustrative example, ESNs of “ESN 1”-“ESN 3” are included in ESN list 354. Provisioning of ESN(s) and/or MEID(s) may be made as part of an initial femtocell system 350 activation. In the illustrative example, femtocell system 350 is allocated an Internet Protocol (IP) address of “66.249.73.42”, and UE 325 is allocated a mobile services ISDN (MSISDN) number, or E.164 number, of “12145551212”.

FIG. 4A is a simplified diagrammatic representation of femtocell system 350 depicted in FIG. 3 that facilitates provisioning of a femto-RAN in accordance with an embodiment. Femtocell system 350 includes an antenna 400 coupled with a BTS 410. BTS 410 may be implemented, for example, as a 1×RTT ASIC device and may comprise a non-diversity receiver featuring a built-in duplexer. In an embodiment, BTS 410 may feature only one operational band and may include a transmitter scan receiver and local oscillator. BTS 410 may be communicatively coupled with a BSC 420 that provides radio control functions, such as receiving measurements from UEs, such as mobile phones, control of handovers to and from other femtocell systems, and may additionally facilitate handoff to or from macrocells.

Femtocell system 350 includes an electronic serial number screening function 430 that may facilitate approving or rejecting service for a UE by femtocell system 350. Additionally femtocell system 350 includes an Internet Operating System (IOS) and SIP Adapter (collectively referred to as IOS-SIP Adapter 440). IOS-SIP adapter 440 may invoke and manage SIP clients, such as a user agent (UA) pool comprising one or more UAs. In accordance with an embodiment, each UE 325 authorized to be serviced by femtocell system 350 may have a UA allocated therefor by femtocell system in a manner that facilitates transmission of communications to and from a UE over an IP backhaul. Accordingly, when an authorized UE is within the femtocell system 350 site range, telecommunication services may be provided to the UE via the IP backhaul and femtocell system 350 provisioned RAN. When the UE is moved beyond the service range of femtocell system 350, telecommunication service may then be provided to the UE via macrocellular coverage.

To facilitate routing of calls from circuit switched call originators, femtocell system 350 may perform a DNS/ENUM registration on behalf of UEs authorized to obtain service from femtocell system 350. In the present example, assume UE 325 with a MSISDN of “12145551212” has a SIP service subscription in the domain “example.com” and has a SIP uniform resource identifier (URI) of “12145551212@example.com”. An example DNS/ENUM registration message generated by femtocell system 350 on behalf of UE 325 and transmitted to DNS 372 is as follows:

$ORIGIN 2.1.2.1.5.5.5.4.1.2.1.e164.arpa.

IN NAPTR 100 10 “u” “E2U+sip” “!^.*$!sip:12145551212@example.com!”.

As is understood, the first line of the registration message comprises the MSISDN number of the UE converted (i.e., reversed with each numeral delineated with a “.” character and appended with the e164.arpa domain) for DNS lookup. The second line of the registration message specifies the NAPTR record for the hosts that can further process the address—the domain “example.com” (in which the UE with a URI of 12145551212@example.com is registered) in the present example.

Femtocell system 350 may generate and issue a SIP registration on behalf of UE 325 authorized for service access by femtocell system 350.

FIG. 4B is a simplified diagrammatic representation of an alternative femtocell system 450 that facilitates provisioning of a femto-RAN in accordance with an alternative embodiment. Femtocell system 450 includes an antenna 400 coupled with a radio node (RN) 411. RN 411 may be implemented, for example, as a 1×EV-DO ASIC device. For example, RN 411 may provide a 1×EV-DO Rev. 0 air interface or a 1×EV-DO Rev. A air interface. RN 411 may be communicatively coupled with a radio network controller (RNC) 421 that provides radio control functions, such as receiving measurements from UEs, control of handovers to and from other femtocell systems, and may additionally facilitate handoff to or from macrocells. RNC 421 may also provide encryption/decryption functions, power, load, and admission control, packet scheduling, and various other services.

Femtocell system 450 includes an electronic serial number screening function 430 that may facilitate approving or rejecting service for a UE by femtocell system 450. Additionally, femtocell system 450 includes an Internet Operating System (IOS) and SIP Adapter (collectively referred to as IOS-SIP Adapter 440). IOS-SIP adapter 440 may invoke and manage SIP clients, such as a user agent (UA) pool comprising one or more UAs. Each UE 325 authorized to be serviced by femtocell system 450 may have a UA allocated therefor by femtocell system 450 in a manner that facilitates transmission of communications to and from a UE over an IP backhaul. Accordingly, when an authorized UE is within the femtocell system 450 site range, telecommunication services may be provided to the UE via the IP backhaul and femtocell system 450 provisioned RAN. When the UE is moved beyond the service range of femtocell system 450, telecommunication service may then be provided to the UE via macrocellular coverage. Femtocell system 450 may perform a DNS/ENUM registration on behalf of UEs authorized to obtain service from femtocell system 450 and may generate and issue a SIP registration on behalf of a UE authorized for service access by the femtocell system 450 in a manner similar to that described above with reference to femtocell system 350.

FIG. 5 is a diagrammatic representation of an exemplary SIP registration message 500 generated by femtocell system 350 on behalf of UE 325 authorized for service access thereby in accordance with an embodiment. Registration message 500 may be transmitted from femtocell system 350 to an IP switch, such as SIP switch 380 that includes a SIP Registrar 382. Registrar 382 may provide the location and contact information to a location server 384. Registration message 500 includes a REGISTER field 510 that specifies the registration is being made within the domain “example.com”. Multiple contacts may be included in registration message 500. In the present example, registration message 500 includes a contact field 512 that specifies a SIP contact for UE 325. Notably, the SIP contact field 512 for UE 325 specifies the UA registered on behalf of UE with the URI 12145551212@exmaple.com is located at the IP address of “66.249.73.42”. That is, the SIP contact registered by femtocell system 350 on behalf of UE 325 is to be addressed at the femtocell system 350 address of 66.249.73.42 thereby resulting in routing of SIP signaling messages to femtocell system 325. In turn, femtocell system 350 may convert SIP call set up messaging to RAN signaling, allocate an uplink and a downlink channel for UE 325, and set up a call or data session thereon.

In the present example, registration message 500 includes a second contact field 514 that specifies a telephone URI, e.g., the MSISDN +1-214-555-1212 of UE 325. Thus, a location query for the SIP URI sip:12145551212@example.com would return two contacts. The first is the SIP URI that can be used to reach femtocell system 350, and thus UE 325 thereby, and the second is the telephone URI that can be used to reach UE 325 via macrocellular coverage, i.e., via RAN 310. As is understood, the order of contacts 512-514 provides a contact preference, and the multiple contacts may be registered in separate registration messages. The depicted registration message including both the SIP contact URI and telephone URI is exemplary only. Accordingly, in the present example, an attempt to contact UE 325 may first be made via the SIP URI 12145551212@example.com. In the event that the session is not successfully set up via the SIP contact, an attempt may be made to setup a session via RAN 310 using the telephone URI.

When the UE 325 moves outside the coverage area of femtocell system 350, another registration may be generated and submitted by femtocell system 350 on behalf of UE 325 where the telephone URI is designated as the preferred contact. Further, the SIP URI may be removed from the registration when the UE 325 moves outside the coverage area of femtocell system 350 thereby avoiding any attempts to establish a session with UE 325 via femtocell system 350 when UE 325 has moved beyond the femtocell system 350 coverage area.

To better facilitate an understanding of disclosed embodiments, consider a call placed at circuit switched telephone 332 to UE 325. A gateway receives the call setup request, e.g., an Initial Address Message (IAM), and a query may be made with DNS 372 from which the domain “example.com” is resolved from the ENUM function. An INVITE message is then transmitted to the example.com domain which, in turn, resolves the location of the called UE 325. Particularly, CSCF 320 may interrogate location server 384 and determine UE 325 is registered as located at the IP address 66.249.73.42. Accordingly, the INVITE message is routed to proxy server 376 which forwards the INVITE message to femtocell system 350. Femtocell system 350 may then perform paging, channel allocation, and other procedures for provisioning a radio interface with UE 325 and issue SIP responses on behalf of UE 325. Thus, from a network perspective, femtocell system 350 appears as a user agent to which the call is directed. Further, UE 325 does not require a SIP client for receiving the call because femtocell system 350 advantageously performs signaling and media conversion for signaling and media transmissions over-the-air interface with 325. Thus, femtocell system 350 may appear as a conventional BTS to UE 325. A call from UE 325 to another terminal, such as circuit-switched telephone 332, a SIP client such as packet-switched telephony device 374 a, or another device, may similarly be facilitated by femtocell system 350.

As a second example, assume UE 325 has moved beyond the range of femtocell system 350. As noted above, femtocell system 350 may generate and transmit a registration message that excludes the SIP contact to facilitate provisioning of telecommunication services via macrocell coverage, e.g., via RAN 310. For instance, femtocell system 350 may periodically perform power measurements with UE 325, and upon the power measurement dropping below a particular power threshold, femtocell system may determine UE 325 is to be serviced by macrocellular coverage. Alternatively, a user may select macrocellular coverage via a user interface provided on UE 325. In this instance, UE 325 may provide an indication to femtocell system 350 that telecommunication services are to be provided by RAN 310. Other scenarios may similarly result in a determination that UE 325 is to be serviced by RAN 310. Upon such a determination, femtocell system 350 may generate and transmit a registration message on behalf of UE 325 to a registrar service, e.g., CSCF 320 and SIP registrar 382. The contact information may then be updated in location server 384 to indicate the telephone URI as the contact of UE 325. In this scenario, consider a call placed at circuit switched telephone 332 to UE 325. A gateway receives the call setup request, e.g., an Initial Address Message (IAM), and a query may be made with DNS server 372 from which the domain “example.com” is resolved from the ENUM service. An INVITE message is then transmitted to the example.com domain which resolves the location of called UE 325. In the present example, CSCF 320 may interrogate location server 384 and determine UE 325 has a preferred contact registered as a telephone URI of 2145551212. Accordingly, the INVITE message is routed to a gateway server, e.g., gateway server 390 which translates the INVITE message to a RAN-compliant call request signaling. The call may then be setup via RAN 310 accordingly.

A network of femtocell systems may be deployed and connected with an IP backhaul. In this implementation, an authorized UE may be serviced by the femtocell network, and service may be transferred from one femtocell to another femtocell via a femtocell handoff procedure. In the event that the femtocell network is deployed in an area serviced by a macrocellular network, handoff routines may provide preference for transferring a UE to a target femtocell system rather than a macrocell site. In the event that a suitable femtocell is unavailable for handoff of a UE, the UE may be transferred to the macrocell site.

FIG. 6 is a diagrammatic representation of a network system 600 featuring a femtocell network implemented in accordance with an embodiment of the invention. System 600 includes a RAN 610 that provides an over-the-air interface with UEs 625 a-625 c, e.g., a mobile terminal. RAN 610 may comprise, for example, a CDMA radio access network or another suitable RAN. RAN 610 may comprise various BTSs 612 a-612 c and associated BSCs 604 as well as other infrastructure as is understood. Each of BTSs 612 a-612 c provide a respective macrocell 602 a-602 c that may provide telecommunication service to UEs 625 a-625 c. BSC 604 is coupled with a MSC 606 that provides cellular exchange services, mobility management, and other services within the area that it serves as is understood.

RAN 610 may interface with IMS 620 adapted to provide IP service to UEs 625 a-625 c. To this end, RAN 610 may be communicatively coupled with a SGSN 614 and a GGSN 616. GGSN 616 is communicatively coupled with a PDF 618 that provides authorization of media plane resources. PDF 618 may be communicatively coupled with a CSCF 620.

CSCF 620 comprises various SIP servers or proxies that process SIP signaling packets in IMS 620. CSCF 620 may include a P-CSCF, a S-CSCF, and an I-CSCF as is understood. HSS 640 stores user profiles that specify subscription-related information of authorized users, authenticates and authorizes users, and provides information about the user's physical location. Various application servers 642 a-642 n may host and execute services and is interfaced with CSCF 620 via SIP.

The I-CSCF has an IP address that is published in DNS 672 that facilitates location of the I-CSCF by remote servers. Thus, the I-CSCF is used as a forwarding point for receipt of SIP packets within the domain.

CSCF 620 is coupled with a BGCF 622 that comprises a SIP server that provides routing functionality based on telephone numbers. A MGCF 624 performs call control protocol conversion between SIP and ISDN User Part (ISUP) and interfaces with a SGW 626 that itself interfaces with the signaling plane of a circuit switched network, e.g., PSTN 630. A MGW 628 interfaces with the media plane of PSTN 630 or another circuit switched network. Resources of MGW 628 are controlled by MGCF 624. Fixed access devices, e.g., IP telephony devices 674 a-674 b, may connect with IMS network via Internet 670 that is communicatively coupled with IMS network 620 by way of border gateway 660. CSCF 620 may interface with a SIP switch 680, or other IP switch, that includes a Registrar 682 that processes register requests and provides location and contact information to a location server 684.

A BSM 678 may be deployed in Internet 670 and may be adapted to communicate with numerous femtocell systems and femtocell networks. BSM 678 may provide various operations, maintenance, and management functions to femtocell systems. BSM 678 may provide service provisioning of femtocell systems, e.g., by providing configuration downloads to femtocell systems and preloading default configuration data for femtocell systems distributed via sales channels. BSM 678 may provide various support and maintenance features, such as alarm and periodic statistics reporting, automatic remote software image distribution to femtocell systems, provide upgrades and reconfigurations, and may provide remote access via Internet 670 for diagnostics and customer support.

Femtocell systems 650 a-650 c may include integrated BTS and BSC, or alternatively (or additionally) radio node (RN) and radio network controller (RNC), functions and may feature additional capabilities available in the provided femtocell site coverage areas. Femtocell systems 650 a-650 c provide an IP-accessible radio access network, are adapted for operation with IMS 620, and provide radio link control functions. Femtocell systems 650 a-650 c may be communicatively coupled with Internet 670 via any variety of backhaul technologies, such as an 802.11x link, a 10/100 BaseT LAN link, a T1/E1 Span or fiber, cable set top box, DSL modem connected with a central office digital subscriber line access multiplexer, a very small aperture terminal (VSAT), or another suitable backhaul infrastructure. In the illustrative example, femtocell systems 650 a-650 c may be coupled with an IP backhaul access device 655, such as an Ethernet cable or DSL router. For instance, femtocell systems 650 a-650 c may be coupled with access node 655 via respective 10/100BaseT twisted pair cables, Category 5 cabling, or other suitable interconnection.

Each of femtocell systems 650 a-650 c provide a respective femtocell site 651 a-651 c in which UEs 625 a-625 c may be provided telecommunication services over an air interface. Femtocell systems 650 a-650 c are communicatively coupled with one another via access device 655. Femtocells 650 a-650 c deployed for conjunctively providing a femtocell service coverage area comprised of the collective femtocell sites 651 a-651 c are collectively referred to herein as a femtocell network. In an embodiment, femtocell systems 650 a-650 c may exchange messages with one another to facilitate handoff of a UE from one femtocell to another, e.g., as UE 625 a moves out of the radio range of a femtocell and into the radio range of another. In the depicted example, the femtocell network provided by femtocell systems 650 a-650 c is at least partially overlapped by one or more macrocell sites 602 a-602 c provisioned by macrocell BTSs 612 a-612 c. In such an implementation, femtocell systems 650 a-650 c may provide preference to another femtocell for handoff of a UE thereto. In the event that another femtocell is not available or is unsuitable for a handoff, the UE may then be transferred to macrocellular coverage via a handoff to a macrocell BTS.

In an embodiment, each of femtocell system 650 a-650 c include a respective SIP adapter that supports a SIP client pool and provides conversion of call set-up functions to SIP client set-up functions. Additionally, femtocell systems 650 a-650 c include ESN and/or MEID screening to allow only designated UEs to access the femtocells thereby restricting access to authorized home or small office UEs. For example, femtocell system 650 a may be configured with an ESN and/or MEID list 654 a that specifies ESNs and/or MEIDs of UEs authorized to access femtocell system 650. In the illustrative example, ESNs of “ESN 1”-“ESN 3” are included in ESN and/or MEID list 654 a. Provisioning of ESN(s) and/or MEID(s) may be made as part of an initial femtocell system 650 activation. Other femtocell systems 650 b-650 c may be similarly configured with an ESN and/or MEID list including ESNs and/or MEIDs of UEs authorized to access the femtocell system network comprised of femtocell systems 650 a-650 c. In the illustrative example, femtocell systems 650 a-650 c are allocated a respective IP address of “66.249.73.42”, “66.249.73.43”, and “66.249.73.44”.

In an embodiment, a private branch exchange (PBX) 656, e.g., an IP-PBX, may be deployed onsite at the SOHO that hosts the femtocell network comprising femtocell systems 650 a-650 c. In the illustrative example, PBX 656 is interconnected with access device 655. PBX 656 may provide telephone exchange services for UEs authorized to access the femtocell network. In an implementation, femtocell systems 650 a-650 c in conjunction with PBX 656 facilitate abbreviated dialing, e.g., 4-digit dialing, between UEs within the femtocell network as described more fully hereinbelow. In an alternative embodiment, an IP switch, such as SIP switch 684, rather than PBX 656 may facilitate abbreviated dialing.

FIG. 7 is a diagrammatic representation of an exemplary software configuration 700 of a UE, such as UE 625 a, adapted for engaging in communications with femtocell systems in accordance with an embodiment. In the exemplary configuration of FIG. 7, the UE is configured with access network-specific software entities 760, e.g., protocol and driver software associated with a particular access network technology, such as CDMA, GSM, UMTS, or another suitable radio access network, and is dependent on the particular cellular and femtocell access technology in which the UE is to be deployed. While configuration 700 depicts a UE adapted for deployment in a single access network technology type, the UE may be implemented as a multi-mode device and may accordingly include a plurality of access-specific entities in accordance with an embodiment. The particular configuration 700 is illustrative only and is provided only to facilitate an understanding of embodiments disclosed herein.

In the illustrative example, configuration 700 includes a cellular modem driver 702 for providing a physical interface with the access network in which the UE is deployed. An access-stratum 704 and a non-access stratum 706 may be included in configuration 700. A cellular radio interface 708 may be communicatively coupled with lower layers of configuration 700 and may additionally interface with network and session management layers, e.g., a network stack 710. Configuration 700 may include an operating system 714, such as Symbian, Blackberry O/S, or another operating system suitable for mobile applications, and may coordinate and provide control of various components within the UE.

Configuration 700 may include a femto application 712 that facilitates femtocell network acquisition and handoff of a UE from a macrocellular network to a femtocell system in accordance with an embodiment. In one implementation, a femtocell or femtocell network, such as that comprising femtocell systems 650 a-650 c, may be acquired by a micro-pilot assisted handoff routine or a mobile assisted handoff routine as described more fully hereinbelow.

Configuration 700 may include a preferred roaming list (PRL) 716 that contains information used during the system selection and acquisition process. PRL 716 indicates which bands, sub-bands and service provider identifiers will be scanned, and the priority of the scan order. In the illustrative example, PRL 716 includes four entries 716 a-716 d that respectively specify four networks (illustratively designated “Femto”, “Macro 1”, “Macro 2”, and “Roam 1”). In the present example, assume “Femto” refers to the network of femtocell systems 650 a-650 c. The femtocell network is specified first in the prioritized list of PRL entries and thus indicates that the femtocell network is the preferred access network. Assume “Macro 1” refers to radio access network 610, and “Macro 2” refers to another cellular network. “Roam 1” specified by PRL entry 716 d may refer to another cellular network that may have a roaming agreement with the UE home network. As is understood, PRL 716 may comprise an acquisition table that specifies a list of frequencies associated with each of the networks specified in the roaming list on which the UE may scan during search of a particular system and may further specify PN offsets thereof. The acquisition table may additionally specify a network type of each listed network and associated channel blocks.

In accordance with an embodiment, abbreviated dialing is supported by the femtocell network operating in conjunction with an on-site PBX 656 or, alternatively, an IP switch or other suitable entity. A user having authorized access to the femtocell network may dial another authorized user using an abbreviated code, e.g., a 4-digit code comprising the 4-digit station number. On receipt of the call request, the femtocell system may evaluate the destination number to determine if it is an abbreviated code. If the dialed number is not an abbreviated code, the femtocell system may direct the call request to the telecommunication core network for processing thereby. If the dialed number is evaluated by the femtocell system as an abbreviated code, the femtocell system may direct the call request to PBX 656 for call handling. In this instance, the PBX may determine if the abbreviated code is a valid code, i.e., if it is assigned to an authorized UE. If so, PBX 656 may then determine if the dialed UE is currently in the femtocell network service area. In the event the dialed UE is in the femtocell network service area, the PBX may then complete the call setup within the femtocell network. If the PBX determines that the dialed UE is not currently in the femtocell network service area, the PBX may direct the call request to the telecommunication core network, e.g., IMS network 620, for processing of the call setup. Alternatively, the femtocell system may direct the call request to an IP switch, such as SIP switch 684, for call handling in the event the dialed number is an abbreviated code. In this instance, the IP switch may determine if the abbreviated code is a valid code and if it is assigned to an authorized UE. If so, the IP switch may then determine if the dialed UE is currently in the femtocell network service area. In the event the dialed UE is in the femtocell network service area, the IP switch may then direct call setup completion within the femtocell network. If the IP switch determines that the dialed UE is not currently in the femtocell network service area, the IP switch may direct processing of the call request to the telecommunication core network.

FIG. 8 is a diagrammatic representation of a PBX data structure 800 that facilitates abbreviated code dialing within a femtocell network in accordance with an embodiment. In the illustrative example, the PBX data structure is implemented as a table although other data structures may be suitably substituted therefor.

Data structure 800 comprises a plurality of records 810 a-810 c (collectively referred to as records 810) and fields 820 a-820 c (collectively referred to as fields 820) in which authorized UE directory numbers and abbreviated codes therewith are stored. Data structure 800 may be stored on a memory device of PBX 656, fetched therefrom by a processor of the PBX, and processed thereby.

Fields 820 a-820 c have a respective label, or identifier, that facilitates insertion, deletion, querying, or other data operations or manipulations of data structure 800. In the illustrative example, fields 820 a-820 c have respective labels of “Directory Number,” “AC,” and “Femto SA”.

Directory Number field 820 a stores directory numbers, e.g., an MSISDN, of UEs that are authorized to access the femtocell network. In the examples provided herein, assume UEs 625 a-625 c are authorized to access the femtocell network comprising femtocell systems 650 a-650 c and further assume that UEs 625 a-625 c respectively have directory numbers of “12145551212”-“12145551214”. AC field 820 b stores abbreviated codes, e.g., the 4-digit station number of the associated UE. Femto SA field 820 c may store a Boolean value that indicates whether the UE associated with a particular data structure record is currently located in the femtocell service area. Thus, for example, UEs 625 a and 625 c having respective directory numbers of “12145551212” and “12145551214” are currently located in the femtocell service area as indicated by the True (T) value of the Femto SA field 820 c, and UE 625 b having a directory number of “12145551213” is not currently located in the femtocell service area as indicated by the False (F) value of the Femto SA field 820 b. In accordance with an embodiment, PBX 656 may receive call setup requests from femtocell systems 650 a-650 c that receive call requests having a destination number entered as an abbreviated code. The PBX may, in turn, evaluate whether the abbreviated code is a valid code and, if so, determine whether the dialed UE is currently located in the femtocell network service area. If the abbreviated code is valid and the dialed UE is within the femtocell network service area, the PBX may setup the call within the femtocell network. If the dialed abbreviated code is a valid code but the dialed UE is not currently in the femtocell network service area, PBX 656 may transmit the call setup request to the IMS network 620 for processing of the call setup.

FIG. 9 is a flowchart 900 that depicts a femtocell call processing routine implemented in accordance with an embodiment. The processing steps of FIG. 9 may be implemented as computer-executable instructions executable by a processing system, such as a femtocell system, in accordance with an embodiment.

The processing routine is invoked (step 902), and a femtocell system receives a call setup request from a UE (step 904). The femtocell system may screen the call originating UE to evaluate whether the UE is authorized to access the femtocell system (step 906). The particular implementation of UE screening is outside the scope of the present disclosure. In the event that the call originating UE is not authorized to access the femtocell system, the femtocell system may reject the call setup (step 908), and the call processing routine cycle may then end (step 916).

Returning again to step 906, if the femtocell system determines the call originating UE is authorized to access the femtocell system, the femtocell system may then evaluate the destination number to which the call is directed to determine if the destination number is an abbreviated code (step 910), e.g., a 4-digit number. In the event that the destination number is not an abbreviated code, the femtocell system may direct the call setup request to IMS network 620 (step 912), and the call processing routine cycle may then end according to step 916. If the destination number is evaluated as an abbreviated code at step 910, the call setup request may be directed from the femtocell system to the femtocell network PBX 656 for completion of the call setup thereby (step 914). In an alternative embodiment, an IP switch, such as SIP switch 684, may be configured for abbreviated code call setup processing. In this implementation, the femtocell system directs the call setup request to the IP switch, rather than a femtocell network PBX, at step 914. The call processing routine cycle may then end according to step 916.

FIG. 10 is a flowchart 1000 that depicts a PBX call processing routine implemented in accordance with an embodiment. The processing steps of FIG. 10 may be implemented as computer-executable instructions executable by a processing system, such as IP-PBX 656 deployed in a femtocell network, in accordance with an embodiment.

The PBX call processing routine is invoked (step 1002), and a call setup request is received by the PBX from a femtocell system (step 1004). The PBX may then evaluate whether the destination abbreviated code is a valid abbreviated code (step 1006). For example, the PBX may interrogate data structure 800 with the destination abbreviated code to determine if an entry of data suture 800 has a matching abbreviated code. If the abbreviated code is not valid, the PBX may then notify the femtocell system of a call failure (step 1008), and the PBX call processing routine cycle may then end (step 1016).

Returning again to step 1006, if the destination abbreviated code is evaluated as a valid abbreviated code, the PBX may then determine whether the UE assigned the dialed abbreviated code is currently within the femtocell network service area (step 1010). For example, the PBX may evaluate the Femtocell SA field 820 c of data structure 800 allocated for the UE with the dialed abbreviated code to determine if the called UE is currently within the service area of the femtocell network. If the called UE is not within the femtocell network service area, the PBX may then route the call setup to the IMS network (step 1012), and the PBX call processing routine cycle may then end according to step 1016. If the PBX determines that the called UE is currently within the femtocell network service area at step 1010, the PBX may then complete the call setup within the femtocell network (step 1014), and the PBX call processing routine cycle may then end according to step 1016. In an alternative embodiment, the femtocell network may not include an IP PBX and SIP switch 684 may be configured for abbreviated code call setup processing. In this implementation, the SIP switch 684 generally performs the processing steps, or suitable substitutions, of those described in FIG. 10. In another embodiment, the PBX functions described above may be incorporated into a femtocell system and the IP PBX may be excluded from the femtocell network.

As described, a communication system featuring an IP-based femtocell system for provisioning communication services to a user equipment is provided. In one implementation, abbreviated dialing is supported by the femtocell network operating in conjunction with an on-site PBX. A user having authorized access to the femtocell network may dial another authorized user using an abbreviated code, e.g., a 4-digit code comprising the 4-digit station number. On receipt of the call request, the femtocell system may evaluate the destination number to determine if it is an abbreviated code. If the dialed number is not an abbreviated code, the femtocell system may direct the call request to the telecommunication core network for processing thereby. If the dialed number is evaluated by the femtocell system as an abbreviated code, the femtocell system may direct the call request to the PBX for call handling. In this instance, the PBX may determine if the abbreviated code is a valid code, i.e., if it is assigned to an authorized UE. If so, the PBX may then determine if the dialed UE is currently in the femtocell network service area. In the event the dialed UE is in the femtocell network service area, the PBX may then complete the call setup within the femtocell network. If the PBX determines that the dialed UE is not currently in the femtocell network service area, the PBX may direct the call request to the telecommunication core network for processing of the call setup.

The flowcharts of FIGS. 9-10 depict process serialization to facilitate an understanding of disclosed embodiments and are not necessarily indicative of the serialization of the operations being performed. In various embodiments, the processing steps described in FIGS. 9-10 may be performed in varying order, and one or more depicted steps may be performed in parallel with other steps. Additionally, execution of some processing steps of FIGS. 9-10 may be excluded without departing from embodiments disclosed herein.

The illustrative block diagrams depict process steps or blocks that may represent modules, segments, or portions of code that include one or more executable instructions for implementing specific logical functions or steps in the process. Although the particular examples illustrate specific process steps or procedures, many alternative implementations are possible and may be made by simple design choice. Some process steps may be executed in different order from the specific description herein based on, for example, considerations of function, purpose, conformance to standard, legacy structure, user interface design, and the like.

Aspects of the present invention may be implemented in software, hardware, firmware, or a combination thereof. The various elements of the system, either individually or in combination, may be implemented as a computer program product tangibly embodied in a machine-readable storage device for execution by a processing unit. Various steps of embodiments of the invention may be performed by a computer processor executing a program tangibly embodied on a computer-readable medium to perform functions by operating on input and generating output. The computer-readable medium may be, for example, a memory, a transportable medium such as a compact disk, a floppy disk, or a diskette, such that a computer program embodying the aspects of the present invention can be loaded onto a computer. The computer program is not limited to any particular embodiment, and may, for example, be implemented in an operating system, application program, foreground or background process, driver, network stack, or any combination thereof, executing on a single processor or multiple processors. Additionally, various steps of embodiments of the invention may provide one or more data structures generated, produced, received, or otherwise implemented on a computer-readable medium, such as a memory.

Although embodiments of the present invention have been illustrated in the accompanied drawings and described in the foregoing description, it will be understood that the invention is not limited to the embodiments disclosed, but is capable of numerous rearrangements, modifications, and substitutions without departing from the spirit of the invention as set forth and defined by the following claims. For example, the capabilities of the invention can be performed fully and/or partially by one or more of the blocks, modules, processors or memories. Also, these capabilities may be performed in the current manner or in a distributed manner and on, or via, any device able to provide and/or receive information. Further, although depicted in a particular manner, various modules or blocks may be repositioned without departing from the scope of the current invention. Still further, although depicted in a particular manner, a greater or lesser number of modules and connections can be utilized with the present invention in order to accomplish the present invention, to provide additional known features to the present invention, and/or to make the present invention more efficient. Also, the information sent between various modules can be sent between the modules via at least one of a data network, the Internet, an Internet Protocol network, a wireless source, and a wired source and via plurality of protocols. 

What is claimed is:
 1. A method, comprising: performing, in a femtocell, an evaluation of a destination number of a second user equipment to which a call related to a call setup request from a first user equipment is directed; and directing the call to a private branch exchange deployed in the femtocell network if the destination number is an abbreviated code of a telephone number derived from the destination number; directing the call to a core network communicatively coupled with the femtocell network if the destination number is not an abbreviated code of a telephone number derived from the destination number.
 2. The method of claim 1 comprising determining the destination number comprises an abbreviated code.
 3. The method of claim 1, where the abbreviated code comprises a four-digit number.
 4. The method of claim 1 comprising transmitting the call setup request to the private branch exchange.
 5. The method of claim 1 comprising: determining that the second user equipment is located in a service area of the femtocell network; and setting up the call in the femtocell network.
 6. The method of claim 1 comprising: determining that the second user equipment is not located in a service area of the femtocell network; and setting up the call in the core network.
 7. The method of claim 1 comprising determining the destination number does not comprise an abbreviated code.
 8. The method of claim 7 comprising transmitting the call setup request to the core network for processing thereby.
 9. A non-transitory computer-readable medium having computer-executable instructions for execution by a processing system, wherein the instructions: perform, within a femtocell of a femtocell network comprising a private branch exchange, an evaluation of a destination number of a second user equipment to which a call is directed, wherein the evaluation determines if the destination number comprises an abbreviated code; and direct the call to the private branch exchange if the destination number comprises the abbreviated code; direct the call to a core network communicatively coupled with the femtocell network if the destination number does not comprise the abbreviated code.
 10. The non-transitory computer-readable medium of claim 9, wherein the destination number comprises a four-digit abbreviated code.
 11. The non-transitory computer-readable medium of claim 9 comprising instructions that receive by the femtocell a call setup request from a first user equipment and transmit the call setup request to the private branch exchange.
 12. The non-transitory computer-readable medium of claim 9 comprising instructions that: determine that the second user equipment is located in a service area of the femtocell network; and set up the call in the femtocell network.
 13. The non-transitory computer-readable medium of claim 9 comprising instructions that: determine that the second user equipment is not located in a service area of the femtocell network; and set up the call in the core network.
 14. The non-transitory computer-readable medium of claim 9, wherein the instructions that perform an evaluation comprise instructions that determine the destination number does not comprise an abbreviated code.
 15. The non-transitory computer-readable medium of claim 9 comprising instructions that transmit the setup request to the core network for processing thereby.
 16. A system, comprising: a packet-switched network; an IP Multimedia subsystem communicatively coupled with the packet-switched network; and a femtocell network communicatively coupled with the packet-switched network, the femtocell network comprising a private branch exchange, wherein the femtocell network includes a femtocell that performs an evaluation to determine whether a destination number of a second user equipment to which a call setup request, from a first user equipment, is directed comprises an abbreviated code, and directs the call to the private branch exchange if the destination number comprises the abbreviated code or directs the call to a core network communicatively coupled with the femtocell network if the destination number does not comprise the abbreviated code.
 17. The system of claim 16, wherein the femtocell determines the destination number comprises a four-digit abbreviated code.
 18. The system of claim 16, wherein the femtocell transmits the setup request to the private branch exchange, wherein the private branch exchange associates directory numbers of authorized user equipment with abbreviated codes.
 19. The system of claim 16, wherein the private branch exchange determines that the second user equipment is located in a service area of the femtocell network and sets up the call in the femtocell network.
 20. The system of claim 16, wherein the private branch exchange determines that the second user equipment is not located in a service area of the femtocell network and transmits the call setup request to the IP Multimedia subsystem to process the call set up request. 